﻿<%@ Page Title="" Language="C#" MasterPageFile="~/acpMaster.Master" AutoEventWireup="true"
    CodeBehind="AgileFacts.aspx.cs" Inherits="ACP.Web.UI.AgileFacts" %>

<asp:Content ID="Content1" ContentPlaceHolderID="HeaderContent" runat="server">
    <meta http-equiv="Content-type" content="text/html; charset=UTF-8" />
    <title>ACPTEST :: Agile Facts</title>
    <meta http-equiv="Content-Language" content="en-us" />
    <script src="/scripts/coda-slider.1.1.1.js" type="text/javascript"></script>
    <style type="text/css">
        *
        {
            margin: 0;
            padding: 0;
        }
        /* I've used a hard CSS reset above, but you should consider a more sophisticated reset, such as this one: http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/ */
        
        p
        {
            text-align: justify;
            margin: 15px 0;
        }
        
        p, ul
        {
            font-size: 12px;
            line-height: 2.0em;
            text-align: justify;
            color: darkblue;
        }
        
        p a, li a
        {
            color: #39c;
            text-decoration: none;
        }
        
        p.intro
        {
            border-bottom: 1px solid #ccc;
            margin-bottom: 20px;
            padding: 20px 0 30px 0;
            text-align: center;
            width: 100%;
        }
        
        p#cross-links
        {
            text-align: left;
        }
        
        p#cross-links
        {
            padding-top: 20px;
            margin-bottom: 30px;
            padding-bottom: 30px;
        }
        .cross-link
        {
            display: inline-block;
            outline: none;
            width: 140px;
            cursor: pointer;
            text-align: left;
            text-decoration: none;
            font: 14px/100% Arial, Helvetica, sans-serif;
            padding: .1em 1em .1em;
            text-shadow: 0 1px 1px rgba(0,0,0,.3);
            -webkit-border-radius: .5em;
            -moz-border-radius: .5em;
            border-radius: .5em;
            -webkit-box-shadow: 0 1px 2px rgba(0,0,0,.2);
            -moz-box-shadow: 0 1px 2px rgba(0,0,0,.2);
            box-shadow: 0 1px 2px rgba(0,0,0,.6);
        }
        
        noscript p, noscript ol
        {
            color: #a00;
            font-size: 13px;
            line-height: 1.4em;
            text-align: left;
        }
        noscript a
        {
            color: #a00;
            text-decoration: underline;
        }
        noscript ol
        {
            margin-left: 25px;
        }
        
        a:focus
        {
            outline: none;
        }
        
        img
        {
            border: 0;
        }
        
        h3
        {
            border-bottom: 1px solid silver;
            margin-bottom: 5px;
            padding-bottom: 3px;
            text-align: left;
        }
        
        
        
        .stripViewer .panelContainer .panel ul
        {
            text-align: left;
            margin: 0 15px 0 30px;
        }
        
        .slider-wrap
        {
            /* This div isn't entirely necessary but good for getting the side arrows vertically centered */
            margin: 20px 0;
            position: relative;
            width: 100%;
            padding-top: 180px;
            padding-bottom: 4 0px;
        }
        
        .mainContainer
        {
            padding-left: 170px;
            width: 80%;
        }
        /* These 2 lines specify style applied while slider is loading */
        .csw
        {
            width: 100%;
            height: 460px;
            background: #fff;
            overflow: scroll;
        }
        .csw .loading
        {
            margin: 200px 0 300px 0;
            text-align: center;
        }
        
        .stripViewer
        {
            /* This is the viewing window */
            position: relative;
            overflow: hidden;
            border: 5px solid #464647; /* this is the border. should have the same value for the links */
            margin: auto;
            width: 700px; /* Also specified in  .stripViewer .panelContainer .panel  below */
            height: auto;
            clear: both;
            background: #fff;
        }
        
        .stripViewer .panelContainer
        {
            /* This is the big long container used to house your end-to-end divs. Width is calculated and specified by the JS  */
            position: relative;
            left: 0;
            top: 0;
            width: 100%;
            list-style-type: none; /* -moz-user-select: none; // This breaks CSS validation but stops accidental (and intentional - beware) panel highlighting in Firefox. Some people might find this useful, crazy fools. */
        }
        
        .stripViewer .panelContainer .panel
        {
            /* Each panel is arranged end-to-end */
            float: left;
            height: 100%;
            position: relative;
            width: 700px; /* Also specified in  .stripViewer  above */
        }
        
        .stripViewer .panelContainer .panel .wrapper
        {
            /* Wrapper to give some padding in the panels, without messing with existing panel width */
            padding: 10px;
        }
        
        .stripNav
        {
            /* This is the div to hold your nav (the UL generated at run time) */
            margin: auto;
            display: none;
        }
        
        .stripNav ul
        {
            /* The auto-generated set of links */
            list-style: none;
        }
        
        .stripNav ul li
        {
            float: left;
            margin-right: 2px; /* If you change this, be sure to adjust the initial value of navWidth in coda-slider.1.1.1.js */
        }
        
        .stripNav a
        {
            /* The nav links */
            font-size: 10px;
            font-weight: bold;
            text-align: center;
            line-height: 32px;
            background: #c6e3ff;
            color: #fff;
            text-decoration: none;
            display: block;
            padding: 0 15px;
        }
        
        .stripNav li.tab1 a
        {
            background: #60f;
        }
        .stripNav li.tab2 a
        {
            background: #60c;
        }
        .stripNav li.tab3 a
        {
            background: #63f;
        }
        .stripNav li.tab4 a
        {
            background: #63c;
        }
        .stripNav li.tab5 a
        {
            background: #00e;
        }
        
        .stripNav li a:hover
        {
            background: #333;
        }
        
        .stripNav li a.current
        {
            background: #000;
            color: #fff;
        }
        
        .stripNavL, .stripNavR
        {
            /* The left and right arrows */
            position: absolute;
            top: 180px;
            text-indent: -9000em;
        }
        
        .stripNavL a, .stripNavR a
        {
            display: block;
            height: 40px;
            width: 40px;
        }
        
        .stripNavL
        {
            left: 0;
        }
        
        .stripNavR
        {
            right: 0;
        }
        
        .stripNavL
        {
            background: url("images/leftarrow-slider.png") no-repeat center;
        }
        
        .stripNavR
        {
            background: url("images/rightarrow-slider.png") no-repeat center;
        }
        .leftMenu
        {
            position: absolute;
            padding-top: 220px;
            padding-left: 50px;
        }
    </style>
    <script type="text/javascript">
        jQuery(window).bind("load", function () {
            jQuery("div#slider1").codaSlider()
            // jQuery("div#slider2").codaSlider()
            // etc, etc. Beware of cross-linking difficulties if using multiple sliders on one page.
        });
    </script>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="cpMain" runat="server">
    <div id="banner">
        <div class="banner_text">
            Agile Facts</div>
    </div>
    <noscript>
        <p>
            Unfortunately your browser does not hava JavaScript capabilities which are required
            to exploit full functionality of our site. This could be the result of two possible
            scenarios:</p>
        <ol>
            <li>You are using an old web browser, in which case you should upgrade it to a newer
                version. We recommend the latest version of <a href="http://www.getfirefox.com">Firefox</a>.</li>
            <li>You have disabled JavaScript in you browser, in which case you will have to enable
                it to properly use our site. <a href="http://www.google.com/support/bin/answer.py?answer=23852">
                    Information on enabling JavaScript</a>.</li>
        </ol>
    </noscript>
    <div class="leftMenu">
        <p id="cross-links">
            <a href="#1" class="cross-link">
                <img height="15px" width="12px" src="images/rightarrow.png" />
                &nbsp;<b>Waterfall Vs Agile</b></a>
            <br />
            <br />
            <a href="#2" class="cross-link">
                <img height="15px" width="12px" src="images/rightarrow.png" />
                &nbsp;<b>Agile Project</b></a>
            <br />
            <br />
            <a href="#3" class="cross-link">
                <img height="15px" width="18px" src="images/downarrow.png" />&nbsp;<b>SCRUM</b></a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#4" class="cross-link">Scrum
                Roles & Artifacts </a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#5" class="cross-link">Responsibilities
                of Scrum Master</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#6" class="cross-link">Release</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#7" class="cross-link">When
                can a sprint be cancelled?</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#8" class="cross-link">Daily
                Scrum</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#9" class="cross-link">Sprint
                Meetings</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#10" class="cross-link">Burn
                down Chart</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#11" class="cross-link">Sprint
                Backlog</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#12" class="cross-link">Definition
                of done</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#13" class="cross-link">Agile
                Estimation models</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#14" class="cross-link">Risk
                areas in Agile</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#15" class="cross-link">XP
                (eXtreme Programming)</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#19" class="cross-link">XP
                INVEST Principles</a>
            <br />
            <br />
            <img height="15px" width="18px" src="images/spacer.png" />&nbsp;<a href="#20" class="cross-link">
                SCRUM VS XP</a>
        </p>
    </div>
    <div style="height:10px;position:relative">
        &nbsp;</div>
    <div class="mainContainer">
        <div class="slider-wrap">
            <div id="slider1" class="csw">
                <div class="panelContainer">
                    <div class="panel" title="Waterfall Vs Agile">
                        <div class="wrapper">
                            <h3>
                                Waterfall Vs Agile</h3>
                            <ul>
                                <li>Waterfall takes time till almost end of the project to deliver working software,
                                    Agile delivers working software within few weeks of project initiation</li>
                                <li>Waterfall has to wait to get customer feedback until the end of the project, Agile
                                    allows customers to give feedback from the early stages of the project</li>
                                <li>Stress levels in Waterfall teams will be high at the end but in Agile the stress
                                    levels are uniform across all the iterations</li>
                                <li>Bugs cannot be uncovered until testing phase in Waterfall whereas in Agile they
                                    will be found and fixed during initial phases</li>
                                <li>Documentation is more in Waterfall but limited in Agile</li>
                                <li>Changes have to be processed through a process in Waterfall whereas in Agile &#8220;Welcoming
                                    changes at any phase of the project is the fundamental characteristic&#8221;</li>
                                <li>Planning is more in Waterfall and action is more in Agile</li>
                            </ul>
                            <p>
                                <a href="#5" class="cross-link" title="Go to Panel 5" style="text-align:center">&#171; Previous</a>  <a href="#2"
                                    class="cross-link" title="Go to Agile Project" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Agile Project">
                        <div class="wrapper">
                            <h3>
                                Agile Project</h3>
                            <p>
                                <ul>
                                    <li>Agile project starts with three processes: Vision, Product road map, Product backlog</li>
                                    <li>Product roadmap depicts the evolution of the product over time. Defines what each
                                        release chunk looks like and provides a timeframe for each delivery.</li>
                                    <li>The agile strategy is to fix resources and schedule, and then work to implement
                                        the highest value features as defined by the customer.</li>
                                    <li><b>Empirical Model</b><br />
                                        <br />
                                        <ul>
                                            <li>Visibility: Processes must be visible to those controlling the process</li>
                                            <li>Inspection: Processes must be inspected frequently and unaccepted variances can
                                                be detected</li>
                                            <li>Adaption: Process inspector takes decision on adjusting the process to adjust the
                                                variances found in the inspection</li></ul>
                                    </li>
                                </ul>
                            </p>
                            <p>
                                <a href="#1" class="cross-link" title="Go to Waterfall Vs Agile" style="text-align:center">&#171; Previous</a>
                                | <a href="#3" class="cross-link" title="Go to SCRUM" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="SCRUM">
                        <div class="wrapper">
                            <h3>
                                SCRUM</h3>
                            <p>
                                <ul>
                                    <li>A Scrum project starts with a vision of the system to be developed. The vision might
                                        be vague at first, perhaps stated in market terms rather than system terms, but
                                        it will become clearer as the project moves forward. The Product Owner is responsible
                                        to those funding the project for delivering the vision in a manner that maximizes
                                        their ROI</li>
                                    <li>Scrum is used for complex work in which it is impossible to predict everything that
                                        will occur. Accordingly, Scrum simply offers a framework and set of practices that
                                        keep everything visible</li>
                                    <li>Scrum addresses the complexity of software development projects by implementing
                                        the inspection, adaptation, and visibility requirements of empirical process control
                                        with a set of simple practices and rules</li>
                                    <li>Scrum stakeholders: The Scrum planning process sets stakeholders&#8217; expectations.
                                        These stakeholders include<br />
                                        <ul>
                                            <li>Those who fund the project (Product owner/Customer)</li>
                                            <li>Those who intend to use the functionality created by the project (end users)</li>
                                            <li>Those who will be otherwise affected by the project</li>
                                        </ul>
                                    </li>
                                    <li>The minimum plan necessary to start a Scrum project consists of a vision and a Product
                                        Backlog</li>
                                    <li>Scrum managers measure and track requirements, not tasks</li>
                                    <li>Scrum makes the team responsible for managing development activities. The team selects
                                        the work that it will do during each Sprint. After that initial selection is made,
                                        it is up to the team to figure out how to do the work at hand. The team decides
                                        how to turn the selected requirements into an increment of potentially shippable
                                        product functionality. The team devises its own tasks and figures out who will do
                                        them.</li>
                                    <li>The team is responsible for managing itself and had full authority to do anything
                                        to meet the Sprint goal within the guidelines, standards, and conventions of the
                                        organization and of Scrum the team is left alone during the Sprint to accomplish
                                        the goals to which it initially committed</li>
                                    <li>Whenever an opportunity arose that was more important than the work selected by
                                        the team for the Sprint, management could abnormally terminate the Sprint. The Team,
                                        the Product Owner, and management would then conduct a new Sprint planning meeting.
                                        The new opportunity would be selected if it truly was the top-priority Product Backlog</li>
                                </ul>
                            </p>
                            <p>
                                <a href="#2" class="cross-link" title="Go to Agile Project" style="text-align:center">&#171; Previous</a>
                                <a href="#4" class="cross-link" title="Go to Scrum Roles & Artifacts" style="float:right;" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Scrum Roles & Artifacts">
                        <div class="wrapper">
                            <h3>
                                Scrum Roles & Artifacts
                            </h3>
                            <p>
                                <ul>
                                    <li>There are only three Scrum roles: the Product Owner, the Team, and the ScrumMaster
                                    </li>
                                    <li>Three artifacts: Product backlog, Spring backlog and Burndown chart</li>
                                    <li>The Product Owner is responsible for representing the interests of everyone with
                                        a stake in the project and its resulting system. The Product Owner achieves initial
                                        and on-going funding for the project by creating the project&#8217;s initial overall
                                        requirements, return on investment (ROI) objectives, and release plans</li>
                                    <li>The Product Backlog defines the functional and non-functional requirements that
                                        the system should meet to deliver the vision, prioritized and estimated. As long
                                        as a product exists, the Product Backlog also exists The Product Owner is responsible
                                        for using the Product Backlog to ensure that the most valuable functionality is
                                        produced first and built upon </li>
                                    <li>The team: The Team is responsible for developing functionality. Teams are self-managing,
                                        self-organizing, and cross-functional, and they are responsible for figuring out
                                        how to turn Product Backlog into an increment of functionality within iteration
                                        and managing their own work to do so. Team members are collectively responsible
                                        for the success of each iteration and of the project as a whole. The dynamics of
                                        self-organization, collaboration, and emergence are best understood when a team
                                        faces a real problem</li>
                                    <li>Scrum Master: The ScrumMaster is responsible for the Scrum process, for teaching
                                        Scrum to everyone involved in the project, for implementing Scrum so that it fits
                                        within an organization&#8217;s culture and still delivers the expected benefits,
                                        and for ensuring that everyone follows Scrum rules and practices. The ScrumMaster&#8217;s
                                        job is to protect the team from impediments during the Sprint. The ScrumMaster is
                                        not the manager of the Team or a project manager; instead, the ScrumMaster serves
                                        the Team, protects them from outside interference, and educates and guides the Product
                                        Owner and the Team in the skillful use of Scrum.</li>
                                    <br />
                                    Scrum Master has to let the Team figure things out on its own. The ScrumMaster role
                                    ensures that this will happen, since the role includes no authority over the Team.
                                    The ScrumMaster is responsible for the process and removing impediments but is not
                                    responsible for managing the development of functionality. ScrumMasters can help
                                    by asking questions and providing advice, but within the guidelines, conventions,
                                    and standards of the organization, the Team is responsible for figuring out how
                                    to conduct its work. The ScrumMaster&#8217;s job is to ensure that the Scrum practices
                                    are followed. Working together, the ScrumMaster and the Team shape the development
                                    process so that it will bring about the best possible results and won&#8217;t let
                                    things get too far off track.
                                    <li>Theme: High level story, Epic: Large Requirements, Story: Small enough entity to
                                        be worked with during sprint planning, Task: Small enough unit of work for actual
                                        implementation.</li>
                                    <li>The authority of the ScrumMaster is largely indirect; it springs mainly from the
                                        ScrumMaster&#8217;s knowledge of Scrum rules and practices and his or her work to
                                        ensure that they are followed. The ScrumMaster is responsible for the success of
                                        the project, and he or she helps increase the probability of success by helping
                                        the Product Owner select the most valuable Product Backlog and by helping the Team
                                        turn that backlog into functionality</li></ul>
                            </p>
                            <p>
                                <a href="#3" class="cross-link" title="Scrum Roles & Artifacts" style="text-align:center">&#171; Previous</a>  <a href="#5"
                                    class="cross-link" title="Responsibilities of Scrum Master" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Responsibilities of Scrum Master">
                        <div class="wrapper">
                            <h3>
                                Responsibilities of Scrum Master</h3>
                            <p>
                                <ul>
                                    <li>Remove the barriers between development and the Product Owner so that the Product
                                        Owner directly drives development.</li>
                                    <li>Teach the Product Owner how to maximize ROI and meet his or her objectives through
                                        Scrum.</li>
                                    <li>Improve the lives of the development team by facilitating creativity and empowerment.</li>
                                    <li>Improve the productivity of the development team in any way possible.</li>
                                    <li>Improve the engineering practices and tools so that each increment of functionality
                                        is potentially shippable.</li>
                                    <li>Keep information about the team&#8217;s progress up-to-date and visible to all parties.</li>
                                    <li>Acts as chief communicator for: Team, Management, Stakeholders</li>
                                    <li>Scrum master IS NOT decision maker</li>
                                    <li>CANNOT COMMIT to dates, budgets, profits etc</li></ul>
                            </p>
                            <p>
                                <a href="#4" class="cross-link" title="Go to Scrum Roles & Artifacts" style="text-align:center">&#171; Previous</a>  <a href="#6"
                                    class="cross-link" title="Go to Release" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Release">
                        <div class="wrapper">
                            <h3>
                                Release
                            </h3>
                            <p>
                                A release can be planned for a duration of 2 to 4 months. A release can contain
                                one or more iterations. Release planning meeting is 1 or 2 days event.
                                <ul>
                                    <li>Inputs:
                                        <ul>
                                            <li>Prioritized product backlog with estimates</li>
                                            <li>Product vision</li>
                                            <li>Team velocity</li>
                                            <li>Agenda</li>
                                            <li>Date (Optional)</li></ul>
                                    </li>
                                    <li>Attendees:
                                        <ul>
                                            <li>Product owner or customer</li>
                                            <li>Delivery team(s)</li>
                                            <li>Agile project manager</li>
                                            <li>Team leads (optional)</li>
                                            <li>Stakeholders (optional)</li></ul>
                                    </li>
                                    <li>Outputs:
                                        <ul>
                                            <li>Release plan
                                                <ul>
                                                    <li>Assumptions</li>
                                                    <li>Risks </li>
                                                    <li>Action items </li>
                                                    <li>Dependencies </li>
                                                    <li>Release backlog</li></ul>
                                            </li>
                                        </ul>
                                    </li>
                                </ul>
                            </p>
                            <p>
                                <a href="#5" class="cross-link" title="Go to Responsibilities of Scrum Master" style="text-align:center">&#171; Previous</a>  <a href="#7"
                                    class="cross-link" title="Go to When can a sprint be cancelled?" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                When can a sprint be cancelled?</h3>
                            <p>
                                <ul>
                                    <li>Before the allocated 2 weeks are over</li>
                                    <li>The team can cancel the Sprint if they feel they are unable to meet the Sprint goal</li>
                                    <li>Management can cancel the Sprint if external circumstances negate the value of the
                                        Sprint goal</li>
                                    <li>If the Sprint is abnormally terminated, the next step is to conduct a new Sprint
                                        planning meeting, where the reason for the termination is reviewed and the revised
                                        product backlog is moved into Sprints</li>
                                </ul>
                            </p>
                            <p>
                                <a href="#6" class="cross-link" title="Go to Release" style="text-align:center">&#171; Previous</a>  <a href="#8"
                                    class="cross-link" title="Go to Daily Scrum" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                Daily Scrum
                            </h3>
                            <p>
                                Is a 15 minutes meeting. The purpose of the meeting is to synchronize the work of
                                all Team members daily and to schedule any meetings that the team needs to forward
                                its progress. It is very useful for socialization and synchronization. Stakeholders
                                are invited/can attend but cannot talk. The Daily Scrum is an excellent place to
                                observe how much progress a team is making.
                            </p>
                            <p>
                                <a href="#7" class="cross-link" title="Go to When can a sprint be cancelled?" style="text-align:center">&#171; Previous</a>  <a href="#9"
                                    class="cross-link" title="Go to Sprint Meetings" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                Sprint Meetings</h3>
                            <p>
                                <ul>
                                    <li>Sprint/iteration planning meeting: This is a 2 part time boxed meeting with 4 hours
                                        for each part. This meeting will happen at the beginning of each sprint/iteration.
                                        The first part of the meeting involves the team working with the Product Owner in
                                        reviewing the prioritized Product Backlog and putting Story Points for each User
                                        Story. The team then commits to a certain number of User Stories for the iteration.
                                        The second portion of the iteration is typically used by the team to create a list
                                        of Tasks for each User Story in the iteration.</li>
                                    <li>Inputs: Product backlog, Team capabilities, Defect/Bug list</li>
                                    <li>Participants: Product Owner, Delivery Team, Customers, Management</li>
                                    <li>Outputs: Sprint goal, Sprint backlog (task list) with detailed task, detailed estimates,
                                        ownership</li>
                                    <li>Sprint review meeting: At the end of the Sprint, a Sprint review meeting is held.
                                        This is a four-hour, time-boxed meeting at which the Team presents what was developed
                                        during the Sprint to the Product Owner and any other stakeholders who want to attend</li>
                                    <li>Sprint Retrospective meeting: After the Sprint review and prior to the next Sprint
                                        planning meeting, the ScrumMaster holds a Sprint retrospective meeting with the
                                        Team. At this two or three-hour, time-boxed meeting, the ScrumMaster encourages
                                        the Team to revise, within the Scrum process framework and practices, its development
                                        process to make it more effective and enjoyable for the next Sprint. Together, the
                                        Sprint planning meeting, the Daily Scrum, the Sprint review, and the Sprint retrospective
                                        constitute the empirical inspection The purpose of the Sprint retrospective is to
                                        inspect how the Scrum process worked during the last Sprint and adjust it to improve
                                        the next Sprint. These meetings are time-boxed at two hours</li>
                            </p>
                            <p>
                                <a href="#8" class="cross-link" title="Go to Daily Scrum" style="text-align:center">&#171; Previous</a>  <a href="#10"
                                    class="cross-link" title="Go to Burn down Chart" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                Burn down Chart
                            </h3>
                            <p>
                                A burn down chart shows the amount of work remaining across time. The burn down
                                chart is an excellent way of visualizing the correlation between the amount of work
                                remaining at any point in time and the progress of the project Team(s) in reducing
                                this work. The intersection of a trend line for work remaining and the horizontal
                                axis indicates the most probable completion of work at that point in time. The burn
                                down chart is the collision of reality (work done and how fast it&#8217;s being
                                done) with what is planned
                            </p>
                            <p>
                                <a href="#9" class="cross-link" title="Go to Sprint Meetings" style="text-align:center">&#171; Previous</a>  <a href="#11"
                                    class="cross-link" title="Go to Sprint Backlog" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                Sprint Backlog
                            </h3>
                            <p>
                                The Sprint Backlog defines the work, or tasks, that a Team defines for turning the
                                Product Backlog it selected for that Sprint into an increment of potentially shippable
                                product functionality. The Team compiles an initial list of these tasks in the second
                                part of the Sprint planning meeting. Tasks should be divided so that each takes
                                roughly 4 to 16 hours to finish. Tasks longer than 4 to 16 hours are considered
                                mere placeholders for tasks that haven&#8217;t yet been appropriately defined. Only
                                the Team can change the Sprint Backlog. The Sprint Backlog is a highly visible,
                                real-time picture of the work that the Team plans to accomplish during the Sprint
                            </p>
                            <p>
                                <a href="#10" class="cross-link" title="Go toBurn down Chart" style="text-align:center">&#171; Previous</a>  <a href="#12"
                                    class="cross-link" title="Go to Definition of done" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                Definition of done
                            </h3>
                            <p>
                                Thoroughly tested, well-structured, and well-written code that has been built into
                                an executable and that the user operation of the functionality is documented, either
                                in Help files or in user documentation. This is the definition of a &#8220;done&#8221;
                                increment
                                <ul>
                                    <li>Build: A build is a compilation of all of the code in a system or subsystem to validate
                                        that all of the code can be pulled together into a clean set of machine-readable
                                        instructions. The build is usually followed by automated tests to ensure that all
                                        of the functionality works</li>
                                    <li>Successful delivery: &#8220;Completed on time, on budget, with all features and
                                        functions as originally specified.&#8221;</li>
                                </ul>
                            </p>
                            <p>
                                <a href="#11" class="cross-link" title="Go to Sprint Backlog" style="text-align:center">&#171; Previous</a>  <a href="#13"
                                    class="cross-link" title="Go to Agile Estimation models" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                Agile Estimation models
                            </h3>
                            <p>
                                <ul>
                                    <li>Story point estimate:
                                        <li>Story points are a unit of measure for expressing the overall size of a user story,
                                            feature, or other piece of work.</li>
                                        <li>It is a relative measure but not exact</li>
                                        <li>A story that is assigned a two should be twice as much as a story that is assigned
                                            a one. It should also be two-thirds of a story that is estimated as three story
                                            points.</li>
                                        <li>The number of story points associated with a story represents the overall size of
                                            the story.</li>
                                        <li>There is no set formula for defining the size of a story.</li>
                                        <li>It involves: Complexity, Uncertainty (risk) and effort</li>
                                        <li>Planning poker: This estimation include all programmers, testers, database engineers,
                                            analysts, user interaction designers, and so on. This works based on consensus model.</li>
                                        <li>NPV = FV/(1+r) to the power n. Example: What is the NPV of 8000 with interest rate
                                            5% in 4 years? </li>
                                </ul>
                            </p>
                            <p>
                                <a href="#12" class="cross-link" title="Go to  Definition of done" style="text-align:center">&#171; Previous</a>  <a href="#14"
                                    class="cross-link" title="Go to Risk areas in Agile" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                Risk areas in Agile</h3>
                            <p>
                                <ul>
                                    <li>Intrinsic Schedule Flaw (estimates that are wrong and undoable from day one, often
                                        based on wishful thinking)</li>
                                    <li>Specification Breakdown (failure to achieve stakeholder consensus on what to build)</li>
                                    <li>Scope Creep (additional requirements that inflate the initially accepted set)</li>
                                    <li>Personnel Loss</li>
                                    <li>Productivity Variation (difference between assumed and actual performance)</li></ul>
                                <br />
                                <h3>
                                    Risk Response strategies in Agile</h3>
                                <ul>
                                    <li>Avoid (Eliminate)</li>
                                    <li>Mitigate (Reduce impact)</li>
                                    <li>Contain (Similar to contingency)</li>
                                    <li>Evade (Similar to Accept)</li></ul>
                            </p>
                            <p>
                                <a href="#13" class="cross-link" title="Go to XP (eXtreme Programming)" style="text-align:center">&#171; Previous</a>  <a href="#15"
                                    class="cross-link" title="Go to Waterfall Vs Agile" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                XP (eXtreme Programming)</h3>
                            <p>
                                <ul>
                                    <li>XP Practices</li>
                                    <table border="1px" cellpadding="0" cellspacing="0" style="font-size: 12px">
                                        <tr>
                                            <th>
                                                Thinking
                                            </th>
                                            <th>
                                                Collaborating
                                            </th>
                                            <th>
                                                Releasing
                                            </th>
                                            <th>
                                                Planning
                                            </th>
                                            <th>
                                                Developing
                                            </th>
                                        </tr>
                                        <tr>
                                            <td>
                                                <ul>
                                                    <li>Pair programming (Driver and Navigator)</li>
                                                    <li>Energized work</li>
                                                    <li>Informative work space</li>
                                                    <li>Root cause analysis</li>
                                                    <li>Retrospectives</li>
                                                </ul>
                                            </td>
                                            <td>
                                                <ul>
                                                    <li>Trust</li>
                                                    <li>Sit together</li>
                                                    <li>Real customer involvement</li>
                                                    <li>Ubiquitous Language (Metaphor)</li>
                                                    <li>Stand-up meetings</li>
                                                    <li>Coding standards</li>
                                                    <li>Iteration demo </li>
                                                    <li>Reporting</li>
                                                </ul>
                                            </td>
                                            <td>
                                                <ul>
                                                    <li>Done done</li>
                                                    <li>No bugs</li>
                                                    <li>Version control</li>
                                                    <li>Ten minutes build</li>
                                                    <li>Continuous integration</li>
                                                    <li>Collective code ownership</li>
                                                    <li>Documentation</li>
                                                </ul>
                                            </td>
                                            <td>
                                                <ul>
                                                    <li>Vision</li>
                                                    <li>Release planning</li>
                                                    <li>Planning game</li>
                                                    <li>Risk management</li>
                                                    <li>Iteration planning</li>
                                                    <li>Slack</li>
                                                    <li>Stories</li>
                                                    <li>Estimating</li>
                                                </ul>
                                            </td>
                                            <td>
                                                <ul>
                                                    <li>Incremental requirements</li>
                                                    <li>Customer tests</li>
                                                    <li>Test Driven Development</li>
                                                    <li>Refactoring</li>
                                                    <li>Sample Design</li>
                                                    <li>Incremental design and architecture</li>
                                                    <li>Spike solutions</li>
                                                    <li>Performance optimization</li>
                                                    <li>Exploratory testing</li>
                                                </ul>
                                            </td>
                                        </tr>
                                    </table>
                                </ul>
                            </p>
                            <p>
                                <a href="#14" class="cross-link" title="Go to Risk areas in Agile" style="text-align:center">&#171; Previous</a>  <a href="#16"
                                    class="cross-link" title="Go to Risk areas in Agile" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                XP (eXtreme Programming) Cntd..</h3>
                            <p>
                                <ul>
                                    <li>XP&#8217;s applicability is based on organizations and people, not types of projects.</li>
                                    <li>XP Team: creating cross-functional teams composed of diverse people who can fulfil
                                        all the team&#8217;s roles.</li>
                                    <li>XP teams sit together in an open workspace. At the beginning of each iteration,
                                        the team meets for a series of activities: an iteration demo, a retrospective, and
                                        iteration planning. This may take 2 to 4 hours total</li>
                                    <li>XP daily stand-up meeting takes 5 to 10 minutes each</li>
                                    <li>On-site customers&#8212;often just called customers&#8212;are responsible for defining the software
                                        the team builds. Customers&#8217; most important activity is release planning</li>
                                    <li>Product manager (product owner) is to maintain and promote the product vision. this
                                        means documenting the vision, sharing it with stakeholders, incorporating feedback,
                                        generating features and stories, setting priorities for release planning, providing
                                        direction for the team&#8217;s on-site customers, reviewing work in progress, leading
                                        iteration demos, involving real customers, and dealing with organizational politics.</li>
                                    <li>XP recommends 1 tester for every 4 programmers</li>
                                    <li>XP leaders are called as coaches. One of the most important things the coaches can
                                        do is to help the team interact with the rest of the organization.</li>
                                    <li>Mentor is someone outside the team who you can turn to for advice.</li>
                                    <li>XP team size: teams with 4 to 10 programmers (5 to 20 total team members). For new
                                        teams, four to six programmers is a good starting point. XP teams can be as small
                                        as one experienced programmer and one product manager</li>
                                    <li>Refactoring: Refactoring is the process of changing the structure of code&#8212;rephrasing
                                        it&#8212;without changing its meaning or behaviour. It&#8217;s used to improve code quality,
                                        to fight off software&#8217;s unavoidable entropy, and to ease adding new features</li>
                                    <li>Technical debt is the total amount of less-than-perfect design and implementation
                                        decisions in your project. This includes quick and dirty hacks intended just to
                                        get something working right now! and design decisions that may no longer apply due
                                        to business changes. Avoid shortcuts, use simple design, refactor relentlessly</li>
                                    <li>Stories: Stories represent self-contained, individual elements of the project. They
                                        tend to correspond to individual features and typically represent one or two days
                                        of work.</li>
                                    <li>An iteration is the full cycle of design-code-verify-release practiced by XP teams.
                                        It&#8217;s a time box that is usually one to three weeks long (1 week for new team)</li>
                                    <li>Velocity is a simple way of mapping estimates to the calendar. It&#8217;s the total of
                                        the estimates for the stories finished in an iteration.</li>
                                </ul>
                            </p>
                            <p>
                                <a href="#15" class="cross-link" title="Go to XP (eXtreme Programming)" style="text-align:center">&#171; Previous</a>  <a href="#17"
                                    class="cross-link" title="Go to Waterfall Vs Agile" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                XP (eXtreme Programming) Cntd..</h3>
                            <p>
                                <ul>
                                    <li>Prerequisites to implement XP practice:<ul>
                                        <li>Management support<ul>
                                            <li>Common work place with pairing stations</li>
                                            <li>Dedicated team members for the specific project</li>
                                            <li>A product manager, onsite customer, integrated testers</li></ul>
                                        </li>
                                        <li>Team agreement<ul>
                                            <li>Team should agree to go for XP practice, otherwise it does not work</li>
                                            <li>One way to help people agree to try XP is to promise to revisit the decision on
                                                a specific date.</li></ul>
                                        </li>
                                        <li>A collocated team<ul>
                                            <li>Team members must sit in same room</li></ul>
                                        </li>
                                        <li>Onsite customer<ul>
                                            <li>Out of all onsite customers the product manager is most important</li>
                                            <li>If he/she is not available to the team then BA or one of the other onsite customers
                                                can act as Proxy to the product manager</li></ul>
                                        </li>
                                        <li>The right team size<ul>
                                            <li>Total in 12 including 4 to 6 programmers</li></ul>
                                        </li>
                                        <li>Use all the practices<ul>
                                            <li>Try to use all XP practices as much as possible</li></ul>
                                        </li>
                                    </ul>
                                    </li>
                                    <li>Recommendations to go with XP implementation:<ul>
                                        <li>A Brand new code database</li>
                                        <li>Strong design skills</li>
                                        <li>A language that is easy to refactor</li>
                                        <li>An experienced programmer coach</li>
                                        <li>A friendly and cohesive team</li></ul>
                                    </li>
                                    <li>Retrospective meeting: Occurs at the end of every iteration. 1 hour time boxed.
                                        All the team members should participate in this but non-team members should not.</li>
                                    <li>Collaborating:<ul>
                                        <li>Trust is essential for the team to thrive.</li>
                                        <li>Sitting together leads to fast, accurate communication.</li>
                                        <li>Real customer involvement helps the team understand what to build.</li>
                                        <li>A ubiquitous language helps team members understand each other.</li>
                                        <li>Stand-up meetings keep team members informed.</li>
                                        <li>Coding standards provide a template for seamlessly joining the team&#8217;s work together.</li>
                                        <li>Iteration demos keep the team&#8217;s efforts aligned with stakeholder goals.</li>
                                        <li>Reporting helps reassure the organization that the team is working well.</li></ul>
                                    </li>
                                    <li>Stand up meeting: At a pre-set time every day, the whole team stands in a circle.
                                        Thirty seconds per person is usually enough for the stand up meeting.</li>
                                    <li>Iteration demo: That is conducted at the end of every iteration. All team members,
                                        product manager, key stakeholders and executive sponsor attend as much as possible.
                                        This meeting should take 10 minutes. If it takes more than 10 minutes then close
                                        it before 30 minutes.</li>
                                    <li>A burn-up chart is an excellent way to get a bird&#8217;s-eye view of the project shows
                                        progress and predicts a completion date</li>
                                    <li>Throughput is the number of features the team can develop in a particular amount
                                        of time</li>
                                </ul>
                            </p>
                            <p>
                                <a href="#16" class="cross-link" title="Go to XP (eXtreme Programming)" style="text-align:center">&#171; Previous</a>  <a href="#18"
                                    class="cross-link" title="Go to Waterfall Vs Agile" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                XP (eXtreme Programming) Cntd..</h3>
                            <p>
                                <ul>
                                    <li>Done done:<ul>
                                        <li>Tested (all unit, integration, and customer tests finished)</li>
                                        <li>Coded (all code written)</li>
                                        <li>Designed (code refactored to the team&#8217;s satisfaction)</li>
                                        <li>Integrated (the story works from end to end&#8212;typically, UI to database&#8212;and fits into
                                            the rest of the software)</li>
                                        <li>Builds (the build script includes any new modules)</li>
                                        <li>Installs (the build script includes the story in the automated installer)</li>
                                        <li>Migrates (the build script updates database schema if necessary; the installer migrates
                                            data when appropriate)</li>
                                        <li>Reviewed (customers have reviewed the story and confirmed that it meets their expectations)</li>
                                        <li>Fixed (all known bugs have been fixed or scheduled as their own stories)</li>
                                        <li>Accepted (customers agree that the story is finished)</li></ul>
                                    </li>
                                    <li>Predicting release dates: risk_adjusted_iterations_remaining = (points_remaining
                                        / velocity * risk_multiplier) + risk_exposure</li>
                                    <li>Calculate # of story points to complete: risk_adjusted_points_remaining = (iterations_remaining
                                        - risk_exposure) * velocity / risk_multiplier</li>
                                    <li>Reports to avoid in XP<ul>
                                        <li>Source lines of code and function points</li>
                                        <li>Number of stories</li>
                                        <li>Velocity</li>
                                        <li>Code quality</li></ul>
                                    </li>
                                    <li>Time travel: Trying to debug for a code fix in older versions in which the bug did
                                        not exist</li>
                                    <li>A spike solution is a technical investigation. It&#8217;s a small experiment to research
                                        the problem.</li>
                                    <li>Automating your build is one of the easiest ways to improve morale and increase
                                        productivity.</li>
                                    <li>A key component of a successful automated build is the local build.</li>
                                    <li>Slow tests are the most common cause of slow builds.</li>
                                    <li>Vertical-market software is developed for many organizations. Like custom development,
                                        however, it&#8217;s built for a particular industry and it&#8217;s often customized for each
                                        customer</li>
                                    <li>Horizontal-market software is the software that&#8217;s intended to be used across a wide
                                        range of industries<ul>
                                            <li>XP reports:</li>
                                            <li>Vision statement</li>
                                            <li>Weekly demo</li>
                                            <li>Release and iteration plans</li>
                                            <li>Burn up chart</li>
                                            <li>If more then</li>
                                            <li>Road map</li>
                                            <li>Status email</li>
                                            <li>Reports to AVOID:</li>
                                            <li>Source lines of code</li>
                                            <li># of stories</li>
                                            <li>Velocity</li>
                                            <li>Code quality</li></ul>
                                    </li>
                                    <li>Throughput is the number of features the team can develop in a particular amount
                                        of time.</li>
                                </ul>
                            </p>
                            <p>
                                <a href="#17" class="cross-link" title="Go to XP (eXtreme Programming)" style="text-align:center">&#171; Previous</a>  <a href="#19"
                                    class="cross-link" title="Go to Waterfall Vs Agile" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                XP INVEST</h3>
                            <p>
                                <ul>
                                    <li>INVEST: Attributes for user story
                                        <img src="images/INVEST.png" />
                                    </li>
                                    <li>Burn up Vs Burn down charts</li>
                                </ul>
                            </p>
                            <p>
                                <a href="#18" class="cross-link" title="Go to XP (eXtreme Programming)" style="text-align:center">&#171; Previous</a>  <a href="#20"
                                    class="cross-link" title="Go to Waterfall Vs Agile" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <div class="panel" title="Sprint or Iteration">
                        <div class="wrapper">
                            <h3>
                                SCRUM VS XP</h3>
                            <p>
                                <ul>
                                    <table border="1px" cellpadding="0" cellspacing="0" style="font-size: 12px">
                                        <tr>
                                            <th>
                                                Scrum
                                            </th>
                                            <th>
                                                XP
                                            </th>
                                        </tr>
                                        <tr>
                                            <td>
                                                product owner
                                            </td>
                                            <td>
                                                Customer
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                scrum master
                                            </td>
                                            <td>
                                                XP coach
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Team
                                            </td>
                                            <td>
                                                Team
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Sprint
                                            </td>
                                            <td>
                                                Iteration
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                sprint planning meeting
                                            </td>
                                            <td>
                                                planning game
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Scrum tends toward a stronger outward (customer) focus
                                            </td>
                                            <td>
                                                XP tends toward a stronger inward (development team) focus
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Scrum is strong on management techniques but offers little to developers.
                                            </td>
                                            <td>
                                                XP is strong on management techniques also AND includes developer guidelines.
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Scrum views the Product Owner as the critical decision maker for the business.
                                            </td>
                                            <td>
                                                XP shares decision making &#8212; technical people make technical decisions; business
                                                people make business decisions.
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Scrum often uses 2-4 week sprints but this is changing. Sprints are getting shorter.
                                            </td>
                                            <td>
                                                XP often uses 1-2 week iterations.
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Scrum teams are self-organizing. They make team decisions about when and how to
                                                do things.
                                            </td>
                                            <td>
                                                XP teams are more structured. Roles and responsibilities are defined and change
                                                periodically.
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Scrum does not endorse any specific engineering practices.
                                            </td>
                                            <td>
                                                XP endorses test-driven-development as the best way to develop software.
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Scrum does not allow changes to stories or swapping of equivalent stores during
                                                a sprint.
                                            </td>
                                            <td>
                                                XP allows changes as long as the total workload is not increased.
                                            </td>
                                        </tr>
                                        <tr>
                                            <td>
                                                Scrum teams determine what they will work on in any given sprint based on the prioritized
                                                backlog.
                                            </td>
                                            <td>
                                                XP teams have less flexibility. They work on stories in strict priority order.
                                            </td>
                                        </tr>
                                    </table>
                                </ul>
                            </p>
                            <p>
                                <a href="#19" class="cross-link" title="Go to XP (eXtreme Programming)" style="text-align:center">&#171; Previous</a>  <a href="#1"
                                    class="cross-link" title="Go to Waterfall Vs Agile" style="float:right;text-align:center;">Next &#187;</a></p>
                        </div>
                    </div>
                    <!-- .panelContainer -->
                    </div>
                    
                </div>
                <!-- #slider1 -->
            </div>
            <!-- .slider-wrap -->
        </div>
        <%--<p id="cross-links">
	Same-page cross-link controls:<br />
	<a href="#1" class="cross-link">Waterfall Vs Agile</a>  <a href="#2" class="cross-link">Agile Project</a>  <a href="#3" class="cross-link">SCRUM</a> | <a href="#4" class="cross-link">Panel 4</a> | <a href="#5" class="cross-link">Panel 5</a>
</p>--%>
</asp:Content>
